All committers have signed the CLA.

Is the change to the fingerprints file intentional? Im not sure this will be backwards compatible, depending on if there are devices in the field that already use the exiting fingerprint

Good catch — that removal wasn't intentional. This branch predated the Sombra Shades/WM25/L-Z and Sombra Shades/SS25/L-Z fingerprints being added to main, so the diff was dropping them.

I've pushed a commit restoring both entries (unchanged, still mapped to window-treatment-battery), so the change is now purely additive — it only adds the Sombra Shades/SOMBRA/Z-M fingerprint (mapped to window-treatment-powerSource and handled by the new sombra sub-driver). No existing fingerprints are removed, so any field devices on WM25/L-Z or SS25/L-Z keep matching. Thanks for catching it!

Hi @Woofser, could you also update this branch? Looks like it's out-of-date with main.

Thanks @cbaumler — done. I've updated the branch, so it's now up to date with main and merges cleanly. Let me know if anything else is needed.

Hi @Woofser, it looks like the branch is still out-of-date with main.

Hi @cbaumler, That's odd. It looked like it went through. It should be good now

Channel deleted.

Test Results

   73 files    518 suites   0s ⏱️
2 956 tests 2 956 ✅ 0 💤 0 ❌
4 863 runs  4 863 ✅ 0 💤 0 ❌

Results for commit d6633f6.

♻️ This comment has been updated with latest results.

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against d6633f6

Looks like two tests are failing.

A falling position reports opening, then settles to partially open
A rising position reports closing, then settles to partially open

d6633f6 should fix the two failures. The settle tests were advancing the mock clock without registering the timer first, so partially_open never fired — added the __create_and_queue_test_time_advance_timer call to match the doConfigure/added tests. Test-only change. Mind re-running the workflow when you get a sec? Thanks!